Adaptive data collection based on fleet-wide intelligence

ABSTRACT

A system for capturing location-based data includes an interface and a processor. The interface is configured to receive a location-based data description for capturing the location-based data. The processor is configured to determine a location based at least in part on the location-based data description, create a location-based data identification job based at least in part on the location, cause execution of the location-based data identification job to a set of vehicle event recorder systems, wherein the location-based data identification job is executed by a vehicle event recorder system of the set of vehicle event recorder systems to acquire sensor data in response to a vehicle being able to acquire the sensor data related to the location of the location-based data identification job, receive the sensor data from the vehicle event recorder system, and determine the location-based data based at least in part on the sensor data.

BACKGROUND OF THE INVENTION

Low frequency monitoring of public space is frequently necessary forlegal or compliance purposes and can be disproportionately expensive.For example, an advertising company might guarantee to its customersthat all billboards will be checked once a week to verify that theadvertising on the billboard is still in good condition. Availableoptions for verifying the billboard condition (e.g., hiring an employeeto drive to view each billboard, dedicating a cellular-enabled camera tocapture and upload images, etc.) are expensive compared to the benefitto the company of checking and the rare occasion that something isfound. Other tasks of low frequency monitoring of public spaces aresimilar—a town checking that its road signs have not been obscured bytrees, checking whether a lane is still blocked by construction,verifying traffic lights and walk/don't walk signs are functioning,etc.—all produce valuable information but can be prohibitively expensiveto manually investigate. This creates a problem where investigations arenot performed and problems that do exist are not identified.

Modern vehicles (e.g., airplanes, boats, trains, cars, trucks, etc.) caninclude a vehicle event recorder in order to better understand thetimeline of an anomalous event (e.g., an accident). A vehicle eventrecorder mounted on a vehicle typically includes a set of sensors—forexample, video recorders, audio recorders, accelerometers, gyroscopes,vehicle state sensors, global positioning system (GPS), etc., thatreport data, which is used to determine the occurrence of or happeningsduring an anomalous event (e.g., a sudden stop, a hard maneuver, acollision, etc.). A vehicle comprising a vehicle event recorder and aset of sensors will likely drive past a target of interest (e.g., abillboard) on a regular basis, however, it can be very difficult toguarantee a given vehicle will perform all necessary data collection forany given task.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of the invention are disclosed in the followingdetailed description and the accompanying drawings.

FIG. 1 is a block diagram illustrating an embodiment of a systemincluding a vehicle event recorder.

FIG. 2 is a block diagram illustrating an embodiment of a vehicle datacenter.

FIG. 3 is a block diagram illustrating an embodiment of a vehicle eventrecorder.

FIG. 4 is a diagram illustrating an embodiment of a map.

FIG. 5 is a diagram illustrating an embodiment of a map.

FIG. 6 is a flow diagram illustrating an embodiment of a process forcapturing location-based data.

FIG. 7 is a flow diagram illustrating an embodiment of a process forpreparing a location-based data identification job.

FIG. 8 is a flow diagram illustrating an embodiment of a process forpausing or stopping a location-based data identification job, ifnecessary.

FIG. 9 is a flow diagram illustrating an embodiment of a process for acapturing location-based data on a vehicle event recorder.

FIG. 10 is a flow diagram illustrating an embodiment of a process fordetermining whether a vehicle event recorder is able to acquire sensordata related to the location of a location-based data identificationjob.

FIG. 11 is a flow diagram illustrating an embodiment of a process forexecuting a location-based data identification job.

FIG. 12 is a flow diagram illustrating an embodiment of a process fordynamic capturing of dynamic event data.

FIG. 13 is a flow diagram illustrating an embodiment of a process fordetermining whether a vehicle event recorder is located appropriately torecord the dynamic event data using one or more sensors.

FIG. 14 is a flow diagram illustrating an embodiment of a process for ainitiating a dynamic request to capture dynamic event data.

FIG. 15 is a flow diagram illustrating an embodiment of a process forcreating additional requests for dynamic event data in the event that adynamic event has changed location.

FIG. 16 is a flow diagram illustrating an embodiment of a process forcreating additional requests for dynamic event data in the event that aconfiguration setting requires modification.

DETAILED DESCRIPTION

The invention can be implemented in numerous ways, including as aprocess; an apparatus; a system; a composition of matter; a computerprogram product embodied on a computer readable storage medium; and/or aprocessor, such as a processor configured to execute instructions storedon and/or provided by a memory coupled to the processor. In thisspecification, these implementations, or any other form that theinvention may take, may be referred to as techniques. In general, theorder of the steps of disclosed processes may be altered within thescope of the invention. Unless stated otherwise, a component such as aprocessor or a memory described as being configured to perform a taskmay be implemented as a general component that is temporarily configuredto perform the task at a given time or a specific component that ismanufactured to perform the task. As used herein, the term ‘processor’refers to one or more devices, circuits, and/or processing coresconfigured to process data, such as computer program instructions.

A detailed description of one or more embodiments of the invention isprovided below along with accompanying figures that illustrate theprinciples of the invention. The invention is described in connectionwith such embodiments, but the invention is not limited to anyembodiment. The scope of the invention is limited only by the claims andthe invention encompasses numerous alternatives, modifications andequivalents. Numerous specific details are set forth in the followingdescription in order to provide a thorough understanding of theinvention. These details are provided for the purpose of example and theinvention may be practiced according to the claims without some or allof these specific details. For the purpose of clarity, technicalmaterial that is known in the technical fields related to the inventionhas not been described in detail so that the invention is notunnecessarily obscured.

A system for capturing location-based data is disclosed. The systemcomprises an interface and a processor. The interface is configured toreceive a location-based data description for capturing thelocation-based data. The processor is configured to determine a locationbased at least in part on the location-based data description, create alocation-based data identification job based at least in part on thelocation, cause execution of the location-based data identification jobto a set of vehicle event recorder systems, wherein the location-baseddata identification job is executed by a vehicle event recorder systemof the set of vehicle event recorder systems to acquire sensor data inresponse to a vehicle being able to acquire the sensor data related tothe location of the location-based data identification job, receive thesensor data from the vehicle event recorder system, and determine thelocation-based data based at least in part on the sensor data.

A system for dynamic capturing of dynamic event data is disclosed. Thesystem comprises an interface and a processor. The interface isconfigured to receive a request for dynamic event data at a vehicleevent recorder. The processor is configured to extract a location and aconfiguration setting from the request, modify a setting associated withcollection of the dynamic event data according to the configurationsetting, wherein the dynamic event data is collected using one or moresensors, determine whether the vehicle event recorder is locatedappropriately to record the dynamic event data using the one or moresensors, in response to determining that the vehicle event recorder islocated appropriately to record the dynamic event data using the one ormore sensors, record the dynamic event data from the one or moresensors, and provide the dynamic event data.

A system for capturing location-based data comprises a system forutilizing a fleet of vehicles, wherein each vehicle includes a vehicleevent recorder coupled to a set of sensors, for capturing data from adistributed set of locations (e.g., identifying objects at specificlocations and at specific times, identifying specific objects at anylocation or within an area or within a time period, etc.). The vehicleevent recorder comprises a system for collecting and processing sensordata during a vehicle trip, for analyzing anomalous events, driverbehaviors, road conditions, behaviors of other vehicles on the road,etc. For example, a vehicle event recorder system is used to create arecord of an accident in order to reduce liability costs. The system forcapturing location-based data comprises a server system in communicationwith the plurality of vehicle event recorders via a network.

In some embodiments, the system receives a location-based datadescription for capturing the location-based data, and determines alocation-based data identification job using the location-based datadescription. For example, the location-based data identification jobcomprises one or more locations for data capture of a target object. Thelocation-based data identification job comprises other information whenappropriate, for example, a travel direction for image capture, an anglefrom the road, model data (e.g., neural network model, machine learningmodel, etc.) for image recognition, a time range for image capture(e.g., the image should be captured between 3 PM and 5 PM), a distancerange for image capture (e.g., the image should be captured by a camerathat is between 10 feet and 50 feet away from the target of interest),an image capture frequency (e.g., an image of the target object shouldbe captured once a month), etc.

In some embodiments, the system determines a set of vehicle eventrecorders for execution of the job. Determination of the set of vehicleevent recorders is based at least in part on factors including vehicleevent recorder job load, vehicle event recorder route, vehicle eventrecorder system processing capacity, vehicle event recorder associatedsensors, etc. The system provides the job to the set of vehicle eventrecorders, and the vehicle event recorders automatically execute the jobduring normal vehicle operation. In the event it is determined that thevehicle event recorder is able to acquire the desired sensor data (e.g.,that the vehicle is near the target, that the vehicle is orientedtowards the target, etc.), the job is executed, and the data captured.The system then receives and processes the sensor data to determine thelocation-based data. The system tracks data receipt and makes adetermination regarding whether the job is complete and should bestopped (e.g., in the event of a job for capturing data once or a fixednumber of times) or paused (e.g., in the event of a job for capturingdata at a predetermined frequency—for example, once per week, once permonth, etc.). In the event the system determines that the job should bestopped or paused, an indication is provided to the vehicle eventrecorder systems.

In some embodiments, the system for capturing location-based dataimproves the computer by transforming a set of independent vehicle eventrecorders on vehicles into a sensor network system capable ofaccomplishing monitoring tasks that would otherwise not be possible orwould be disproportionately expensive. Monitoring can be accomplished asa background process on the vehicle event recorder and without requiringthe vehicle driver to modify the route or perform any special tasks.

In some embodiments, a system for dynamic capturing of dynamic eventdata comprises a vehicle event recorder system for dynamic capturing ofdynamic event data. The vehicle event recorder system receives a requestfor dynamic event data (e.g., from a vehicle data center), wherein therequest for dynamic event data comprises a location and/or aconfiguration setting. The request for dynamic event data comprises arequest to capture a dynamic event—for example, an event alreadyunderway, an event with a limited duration, etc. The location comprisesthe dynamic event location. The configuration setting comprises aconfiguration setting for dynamically modifying a sensor configuration(e.g., in order to better capture the dynamic event). When the systemfor dynamic capturing of dynamic event data receives the request, itmodifies a setting associated with collection of the dynamic event dataaccording to the configuration setting. For example, system for dynamiccapturing of dynamic event data modifies a video frame rate setting, avideo resolution setting, an accelerometer sample rate setting, anaccelerometer power level, a global positioning system (GPS) sample ratesetting, an audio sensor sample rate, etc. The system then monitors itslocation and orientation, and in response to determining that it islocated appropriately to record the dynamic event data, the data isrecorded.

In various embodiments, a dynamic event comprises an accident that hasrecently occurred and is blocking traffic, an animal loose on citystreets, a crime in progress, or any other appropriate event. In theevent a first vehicle event recorder on a first vehicle captures dataindicating a dynamic event and provides the data to the vehicle datacenter, the vehicle data center creates a request for dynamic event dataand provides the request for dynamic event data to a set of vehicleevent recorders on vehicles in the vicinity of the dynamic event. As aresult of the fast-moving nature of the dynamic event, a higher thantypical sensor resolution is likely to be necessary to capture the eventdata. Sensor configuration settings are determined by the vehicle datacenter (e.g., based at least in part on the event type, the eventlocation, etc.) and are provided as part of the request for dynamicevent data. In response to a receipt of dynamic event data from avehicle event recorder, the vehicle data center is able to make adetermination that the dynamic event data is satisfactory, or that thedynamic event data is not satisfactory and needs to be captured again.In the event the vehicle data center determines that the dynamic eventdata is satisfactory, the vehicle data center provides an indication tostop collecting dynamic event data. In the event that the vehicle datacenter determines that the dynamic event data is not satisfactory, thevehicle data center is able to immediately create a new request fordynamic event data and provide the new request for dynamic event data toone or more vehicle event recorders. The new request for dynamic eventdata can include a new location, a new configuration setting orsettings, and/or be provided to a new set of vehicle event recorders.

In some embodiments, the system for dynamic capturing of dynamic eventdata improves the computer by allowing quickly changing dynamic eventsto be captured based on a dynamic request to fleet vehicles on theirnormal routes through a city. A remote request can be used to modifyconfiguration settings in order to acquire high-resolution imagery usinga sensor device typically used in a low-resolution mode.

FIG. 1 is a block diagram illustrating an embodiment of a systemincluding a vehicle event recorder. Vehicle event recorder 102 comprisesa vehicle event recorder mounted in a vehicle (e.g., a car or truck).Vehicle event recorder 102 is in communication with vehicle sensors 104.Vehicle sensors 104 comprises a set of sensors—for example, one or morevideo recorders (e.g., one or more forward facing video recorders, oneor more side facing video recorders, one or more rear facing videorecorders, one or more interior video recorders, etc.), audio recorders(e.g., one or more exterior audio recorders, one or more interior audiorecorders, etc.), accelerometers, gyroscopes, vehicle state sensors,proximity sensors (e.g., a front distance sensor, a side distancesensor, a rear distance sensor, etc.), advanced driver assistance system(ADAS) sensors, a GPS, outdoor temperature sensors, moisture sensors,line tracker sensors (e.g., laser line tracker sensors), a lane changesensor, etc. Vehicle state sensors comprise internal vehicle statesensors—for example a speedometer, an accelerator pedal sensor, a brakepedal sensor, an engine revolutions per minute (RPM) sensor, an enginetemperature sensor, a headlight sensor, an airbag deployment sensor,driver and passenger seat weight sensors, an anti-locking brake sensor,traction control system sensors, drive wheel speed sensors, shockssensors, an engine exhaust sensor, a gear position sensor, a cabinequipment operation sensor, an engine control unit (ECU) sensor, etc.Vehicle event recorder 102 comprises a system for receiving andprocessing sensor data. Processing sensor data comprises filtering data,identifying patterns in data, detecting events, etc. Vehicle eventrecorder 102 is mounted on vehicle 106 in any appropriate location—forexample, the chassis, the front grill, the dashboard, the rear-viewmirror, the rear window or wall, the floor, etc. There are times whenvehicle event recorder 102 comprises multiple units mounted in differentlocations within vehicle 106 instead of a single unit, particularly whenthere are space constraints for a given location (e.g., behind the rearview mirror) and more space is required to house electronic components.For example, vehicle event recorder 102 comprises a system for dynamiccapturing of dynamic event data, comprising an interface configured toreceive a request for dynamic event data at a vehicle event recorder anda processor configured to extract a location and a configuration settingfrom the request, modify a setting associated with collection of thedynamic event data according to the configuration setting, wherein thedynamic event data is collected using one or more sensors, determinewhether the vehicle event recorder is located appropriately to recordthe dynamic event data using the one or more sensors, in response todetermining that the vehicle event recorder is located appropriately torecord the dynamic event data using the one or more sensors, record thedynamic event data, and provide the dynamic event data.

Vehicle event recorder 102 comprises a communications system forcommunicating with network 100. Network 100 comprises a network forcommunications. Network 100 comprises one or more of a wireless network,a wired network, a cellular network, a Code Division Multiple Access(CDMA) network, a Global System for Mobile Communication (GSM) network,a Long-Term Evolution (LTE) network, a Universal MobileTelecommunications System (UMTS) network, a Worldwide Interoperabilityfor Microwave Access (WiMAX) network, a Dedicated Short-RangeCommunications (DSRC) network, a Message Queueing for TelemetryTransport (MQTT) network, a local area network, a wide area network, theInternet, etc. There are instances when network 100 comprises multiplenetworks, for instance, multiple interconnected networks spanningdifferent regions, networks operating at different times, overlaidnetworks with different access permissions, networks with differentbandwidth, etc. Different networks comprising network 100 typicallycomprise different bandwidth cost (e.g., a wired network has a very lowcost, a wireless Ethernet connection has a moderate cost, and a cellulardata network has a high cost). In some embodiments, network 100 has adifferent cost at different times (e.g., a higher cost during the dayand a lower cost at night).

Vehicle event recorder 102 communicates with vehicle data center 108 vianetwork 100. Vehicle data center 108 comprises a remote server for datastorage, data analysis, data access by a coach and/or manager, datareview by a human reviewer, etc.

In some embodiments, vehicle data center 108 comprises a system forcapturing location-based data, comprising an interface configured toreceive a location-based data description for capturing thelocation-based data and a processor configured to determine a locationbased at least in part on the location-based data description, create alocation-based data identification job based at least in part on thelocation and the configuration setting, cause execution of thelocation-based data identification job to a set of vehicle eventrecorder systems, wherein the location-based data identification job isexecuted by a vehicle event recorder system of the set of vehicle eventrecorder systems to acquire sensor data in response to a vehicle beingable to acquire the sensor data related to the location of thelocation-based data identification job, receive the sensor data from thevehicle event recorder system, and determine the location-based databased at least in part on the sensor data.

In some embodiments, vehicle event recorder 102 comprises a system fordynamic capturing of dynamic event data. Vehicle event recorder 102comprises an interface and a processor. The interface is configured toreceive a request for dynamic event data at a vehicle event recorder.The processor is configured to extract a location and a configurationsetting from the request, modify a setting associated with collection ofthe dynamic event data according to the configuration setting, whereinthe dynamic event data is collected using one or more sensors, determinewhether the vehicle event recorder is located appropriately to recordthe dynamic event data using the one or more sensors, in response todetermining that the vehicle event recorder is located appropriately torecord the dynamic event data using the one or more sensors, record thedynamic event data, and provide the dynamic event data.

FIG. 2 is a block diagram illustrating an embodiment of a vehicle datacenter. In some embodiments, vehicle data center 200 comprises vehicledata center 108 of FIG. 1 . In various embodiments, vehicle data center200 comprises a computer, a networked set of computers, a cloudcomputing system, or any other appropriate vehicle data center system.In the example shown, vehicle data center 200 comprises interface 202.For example, interface 202 comprises an interface for receiving a datasystem, receiving sensor data, receiving a location-based datadescription, receiving network communications, providing an indicationof an anomalous event, providing a job to a vehicle event recorder,providing sensor data, providing communications, providing coachinginformation, etc. Processor 204 comprises a processor for executingapplications 206. Applications 206 comprise location-based data captureapplication 208, job creation application 210, and other applications212. Location-based data capture application 208 comprises anapplication for coordinating a location-based data capture process forcapturing location-based data. For example, locating application 208comprises an application for determining a location based at least inpart on a location-based data description, creating a location-baseddata identification job (e.g., using job creation application 210) basedat least in part on the location and the configuration setting, causingexecution of the location-based data identification job to a set ofvehicle event recorder systems, wherein the location-based dataidentification job is executed by a vehicle event recorder system of theset of vehicle event recorder systems to acquire sensor data in responseto a vehicle being able to acquire the sensor data related to thelocation of the location-based data identification job, receiving thesensor data from the vehicle event recorder system, and determining thelocation-based data based at least in part on the sensor data. Jobcreation application 210 comprises an application for building alocation-based data capture job. For example, job creation application210 comprises an application for determining data capture instructionsbased at least in part on a set of locations. Other applications 212comprise any other appropriate applications (e.g., a communicationsapplication, a data storage and retrieval application, a web browserapplication, a user interface application, a data analysis application,etc.). Storage 214 comprises location-based data 216 (e.g., processedsensor data indicating located items and/or metadata associated with thesensor data—for example, time, date, location, vehicle event recorderidentifier, etc.) and vehicle event recorder data 218 (e.g., vehicleevent recorder hardware capabilities, scheduled jobs, planned routes,etc.). Memory 220 comprises executing application data 222 comprisingdata associated with applications 206.

FIG. 3 is a block diagram illustrating an embodiment of a vehicle eventrecorder. In some embodiments, vehicle event recorder 300 comprisesvehicle data center 102 of FIG. 1 . For example, vehicle event recorder300 comprises one or more devices mounted in a vehicle (e.g., one ormore devices communicating via a wired or wireless communication link).In the example shown, vehicle event recorder 300 comprises interface302. For example, interface 302 comprises an interface for receiving adata system software and/or model, receiving sensor data, receiving arequest for dynamic event data, receiving network communications,providing sensor data configuration information, providing an indicationof an anomalous event, receiving a job for a vehicle event recorder,providing sensor data, providing communications, providing coachinginformation, etc. Processor 304 comprises a processor for executingapplications 306. Applications 306 comprise dynamic event captureapplication 308, configuration setting application 310, and otherapplications 312. Dynamic event capture application 308 comprises anapplication for dynamic capturing of dynamic event data. For example,configuration setting application 310 comprises an application forextracting a location and a configuration setting from a request, modifya setting associated with collection of the dynamic event data accordingto the configuration setting, wherein the dynamic event data iscollected using one or more sensors, determine whether the vehicle eventrecorder is located appropriately to record the dynamic event data usingthe one or more sensors, in response to determining that the vehicleevent recorder is located appropriately to record the dynamic event datausing the one or more sensors, record the dynamic event data, andprovide the dynamic event data. Configuration setting application 310comprises an application for setting a sensor data configuration. Forexample, configuration setting application 310 comprises an applicationfor receiving a configuration setting received by vehicle event recorder300 as part of a request for dynamic event data, determining a sensorconfiguration change message to effect the configuration setting change,and providing the sensor configuration change message to the sensor(e.g., via interface 302). Other applications 312 comprise any otherappropriate applications (e.g., a communications application, a datastorage and retrieval application, a web browser application, a userinterface application, a data analysis application, etc.). Storage 314comprises configuration data 316 (e.g., configuration settings receivedas part of a request for dynamic event data) and sensor data 318 (e.g.,sensor data received from one or more sensors, etc.). Memory 320comprises executing application data 322 comprising data associated withapplications 306.

FIG. 4 is a diagram illustrating an embodiment of a map. In the exampleshown, map 400 comprises an area map including vehicle 402 followingroute 404. Vehicle 402 includes a vehicle event recorder (e.g., vehicleevent recorder 102 of FIG. 1 ). A request to capture an image ofbillboard 406 has been received by a vehicle data center (e.g., vehicledata center 108 of FIG. 1 ). The vehicle data center determines that thevehicle event recorder mounted on vehicle 402 will be able to capturethe image of billboard 406 in the course of its usual route, creates alocation-based data identification job comprising instructions forcapturing the image of billboard 406, and provides the location-baseddata identification job to vehicle 402. Vehicle 402 conducts its normalroute. When the vehicle event recorder mounted on vehicle 402 determinesit is able to capture the image of billboard 406 (e.g., when the vehicleis within a threshold distance of billboard 406 and oriented towardbillboard 406), the job is executed and the image captured. Image datais provided to the vehicle data center for processing. In someembodiments, a time frame is considered for the job—for example, the jobexecutes data capture only once or twice per week, month, year, or anyother appropriate time rate.

FIG. 5 is a diagram illustrating an embodiment of a map. In the exampleshown, map 500 comprises an area map including vehicle 502 and vehicle506, each vehicle including a vehicle event recorder (e.g., vehicleevent recorder 102 of FIG. 1 ) in communication with a vehicle datacenter (e.g., vehicle data center 108 of FIG. 1 ). Vehicle 502 followsroute 504. In the example shown, the vehicle event recorder mounted onvehicle 506 captures an image of incident 508. For example, incident 508comprises a car fire. The vehicle event recorder mounted on vehicle 506provides the image data and location data to the vehicle data center.The vehicle data center determines that vehicle 502 will be able tocapture more data of incident 508 and provides a request for dynamicevent data to the vehicle event recorder mounted on vehicle 502. Therequest for dynamic event data comprises the location of incident 508and a configuration setting indicating—for example, to increase a videocamera capture resolution as vehicle 502 is nearby incident 508. Vehicle502 conducts its normal route. When the vehicle event recorder mountedon vehicle 502 determines it is able to capture the image of incident508 (e.g., when the vehicle is within a threshold distance of incident508 and oriented toward incident 508), the image is captured. Image datais provided to the vehicle data center for processing. In someembodiments, additional vehicles (not shown) are tasked with jobscapturing more data associated with incident 508.

FIG. 6 is a flow diagram illustrating an embodiment of a process forcapturing location-based data. In some embodiments, the process of FIG.6 is implemented by vehicle data center 108 of FIG. 1 . In the exampleshown, in 600, a location-based data identification job is prepared. Forexample, preparing a location-based data identification job comprisesreceiving a location-based data description, determining a location,determining a target, creating a location-based data identification job,etc. In 602, a set of vehicle event recorder systems is determined(e.g., a set of vehicle event recorder systems for executing thelocation-based data identification job). For example, the set of vehicleevent recorder systems is determined based at least in part on vehicleroutes, vehicle speeds, vehicle event recorder hardware, vehicle eventrecorder jobs, tenant or client permissions, location permissions,business rules, legal location permissions, federal laws, state laws, orlocal laws. In 604, execution of the location-based data identificationjob is caused to the set of vehicle event recorder systems, wherein thelocation-based data identification job is executed by a vehicle eventrecorder system of the set of vehicle event recorder systems to acquiredata in response to the vehicle being able to acquire the sensor datarelated to the location of the location-based data identification job.In some embodiments, causing execution of the location-based dataidentification job to the set of vehicle event recorder systemscomprises causing sending of the sensor data from the vehicle eventrecorder system. In 606, the sensor data is received from the vehicleevent recorder system. In 608, the location-based data is determinedbased at least in part on the sensor data. For example, it is determinedwhether the data satisfies all or part of the job criteria or none ofthe job criteria. In 610, it is determined to pause or stop thelocation-based data identification job, if necessary. For example, inresponse to the data satisfying all or part of the criteria, it isdetermined whether the job should be halted or paused in some or all ofthe set of vehicle event recorders. In various embodiments, the job ispaused or halted based on whether the vehicle event recorders are orcontinue to or will be in an appropriate location at an appropriate timeto satisfy the job.

FIG. 7 is a flow diagram illustrating an embodiment of a process forpreparing a location-based data identification job. In some embodiments,the process of FIG. 7 implements 600 of FIG. 6 . In the example shown,in 700, a location-based data description for capturing a location-baseddata is received. For example, the location-based data descriptioncomprises one or more locations, one or more viewing directions (e.g.,directions along which the location-based data are to be viewed), one ormore object types, one or more capture frequencies (e.g., frequenciesindicating how often object data is to be collected), one or more datacollection time windows (e.g., a time of data for data collection, adeadline by which data must be collected, etc.), one or more geofenceregions (e.g., regions within which it is determined whether target datais able to be acquired), etc. In 702, a location is determined based atleast in part on the location-based data description. In someembodiments, a plurality of locations are determined. For example, thelocation is extracted from the location-based data description. In 704,a target is determined based at least in part on the location-based datadescription. For example, the target comprises a road sign, a billboard,a building, a road feature, or a construction zone. In 706, alocation-based data identification job is created based at least in parton the location. The location-based job comprises location-based datacollection instructions for collecting location-based data. In someembodiments, the location-based job is based at least in part on thetarget. In some embodiments, creating the location-based job comprisesdetermining a geofence region including the location. For example, thegeofence region comprises a geographical perimeter or a road segment. Insome embodiments, a vehicle event recorder is configured to determinewhether the vehicle (e.g., the vehicle it is mounted on) is able toacquire sensor data related to the location of the location-based dataidentification job while the vehicle is within the geofence region. Insome embodiments, the processor is further configured to determine amodel-based system comprising a portion of the location-based dataidentification job. For example, a model-based system comprises amachine learning system, a neural network system, an artificialintelligence system, a machine vision system, etc. Determining a modelbased system comprises determining a set of parameters describing amodel of a model-based system (e.g. a set of neural network weights or aset of machine learning feature weights). In some embodiments, thelocation-based data identification job additionally comprises arecognition frequency (e.g., a number of times the data needs to becaptured per period of time—for example, once or twice a day, a week, amonth, a year, etc.).

In 708, it is determined whether previously captured data satisfies alocation-based data description. For example, previously captured datacomprises previously captured data stored by the vehicle data center. Inthe event it is determined that previously captured data does notsatisfy the location-based data description, the process ends. In theevent it is determined that previously captured data satisfies thelocation-based data description, control passes to 710. In 710, thelocation-based data is determined based at least in part on thepreviously captured data.

FIG. 8 is a flow diagram illustrating an embodiment of a process forpausing or stopping a location-based data identification job, ifnecessary. In some embodiments, the process of FIG. 8 implements 610 ofFIG. 6 . In the example shown, in 800, it is determined whether a timebound has been reached. A time bound comprises a time after which thelocation-based data identification job should no longer be executed. Forexample, a time bound comprises a time bound received as part of alocation-based data description. In the event it is determined in 800that a time bound has been reached, control passes to 802. In 802, anindication is provided to cease execution of the location-based dataidentification job. For example, the indication is provided to a set ofvehicle event recorder systems. In the event it is determined in 800that a time bound has not been reached, control passes to 804. In 804,it is determined whether received location-based data satisfies afrequency constraint. For example, determining that the location-baseddata satisfies a frequency constraint comprises determining that thelocation-based data has been located and does not need to be locatedagain for a predetermined period of time (e.g., receiving location-baseddata at least a threshold number of times within a predetermined periodof time). In the event it is determined that received location-baseddata does not satisfy a frequency constraint, the process ends. In theevent it is determined that received location-based data satisfies afrequency constraint, control passes to 806. In 806, an indication isprovided to the set of vehicle event recorder systems to not execute thejob for a period of time based at least in part on a recognitionfrequency.

FIG. 9 is a flow diagram illustrating an embodiment of a process for acapturing location-based data on a vehicle event recorder. In someembodiments, the process of FIG. 9 is executed by vehicle event recorder102 of FIG. 1 . In the example shown, in 900, a location-based dataidentification job comprising a location-based data description isreceived. For example, the location-based data identification job isreceived from a vehicle data center (e.g., vehicle data center 108 ofFIG. 1 ). In 902, it is determined whether previously captured datastored on the vehicle event recorder satisfies the location-based datadescription. In the event it is determined that previously captured datastored on the vehicle event recorder does not satisfy the location-baseddata description, control passes to 906. In the event it is determinedthat previously captured data stored on the vehicle event recordersatisfies the location-based data description, control passes to 904. In904, the previously captured data is provided. In 906, it is determinedwhether a geofence region associated with the location-based dataidentification job has been entered. In the event it is determined thatthe geofence region associated with the location-based dataidentification job has not been entered, control passes to 912. In theevent it is determined that the geofence region associated with thelocation-based data identification job has been entered, control passesto 908. In 908, it is determined whether the vehicle event recorder isable to acquire sensor data related to the location of thelocation-based data identification job. In the event it is determinedthat the vehicle event recorder is not able to acquire sensor datarelated to the location of the location-based data identification job,control passes to 912. In the event it is determined that the vehicleevent recorder is able to acquire sensor data related to the location ofthe location-based data identification job, control passes to 910. In910, the location-based data identification job is executed. In 912, itis determined whether to continue collecting data. In the event it isdetermined to continue collecting data, control passes to 906. In theevent it is determined not to continue collecting data, the processends.

FIG. 10 is a flow diagram illustrating an embodiment of a process fordetermining whether a vehicle event recorder is able to acquire sensordata related to the location of a location-based data identificationjob. In some embodiments, the process of FIG. 10 implements 908 of FIG.9 . In the example shown, in 1000, it is determined whether the vehicleevent recorder is within a threshold distance of the location. Forexample, it is determined whether the vehicle event recorder is within athreshold distance of the location based at least in part on a GPSmeasurement. In the event it is determined that the vehicle eventrecorder is not within a threshold distance of the location, the processends. In the event it is determined that the vehicle event recorder iswithin a threshold distance of the location, control passes to 1002. In1002, it is determined whether the vehicle event recorder is receivingdata from a sensor oriented toward the location. For example, it isdetermined whether the vehicle event recorder is receiving data from asensor oriented toward the location based at least in part on sensororientation information (e.g., a relative orientation associated with aset of sensors mounted on the vehicle, a direction of motion data, etc.)and a set of GPS measurements or a GPS measurement and a compassmeasurement. In the event it is determined that the vehicle eventrecorder is not receiving data from a sensor oriented toward thelocation, the process ends. In the event it is determined that thevehicle event recorder is receiving data from a sensor oriented towardthe location, control passes to 1004. In 1004, additional locationconstraints and/or direction constraints are determined. For example,additional location constraints and/or direction constraints comprise atighter distance threshold, a constraint depending on both distance andorientation, a constraint dependent on number of other vehicles present,a constraint dependent on time of day, a constraint dependent on vehicletravel speed, etc. In some embodiments, additional location constraintscomprise model-based constraints (e.g., does a model-based processing ofa sensor input indicate that the vehicle event recorder is able toacquire sensor data related to the location of a location-based dataidentification job). In some embodiments, no additional location and/ordirection constraints are determined. In 1006, it is determined whetherthe additional location constraints and/or direction constraints aresatisfied. In the event it is determined that the additional locationconstraints and/or direction constraints are not satisfied, the processends. In the event it is determined that the additional locationconstraints and/or direction constraints are satisfied, control passesto 1008. In some embodiments, there are no additional locationconstraints and/or direction constraints allowed by the system, and step1006 is omitted with the process of FIG. 10 flowing from 1004 directlyto 1008. In 1008, the process indicates that the vehicle is able toacquire sensor data related to the location of the location-based dataidentification job.

FIG. 11 is a flow diagram illustrating an embodiment of a process forexecuting a location-based data identification job. In some embodiments,the process of FIG. 11 implements 910 of FIG. 9 . In the example shown,sensor data comprising the location-based data is received. For example,data is received from one or more sensors. In 1102, the location-baseddata is stored. For example, the data is stored in a memory local to thevehicle event recorder. In 1104, the location-based data is provided toa vehicle data server. For example, the data is copied from the storedlocation in memory local to the vehicle event recorder and transmittedto the vehicle data server (e.g., transmitted via a cellular datanetwork or a WiFi connection, etc.).

FIG. 12 is a flow diagram illustrating an embodiment of a process fordynamic capturing of dynamic event data. In some embodiments, theprocess of FIG. 12 is executed by a vehicle event recorder (e.g.,vehicle event recorder 102 of FIG. 1 ). In the example shown, in 1200, arequest for dynamic event data is received at a vehicle event recorder.In some embodiments, the request for dynamic event data is received froma server system (e.g., a vehicle data center). For example, dynamicevent data comprises data describing a limited duration event (e.g., anevent in progress, a moving event, an event that may stop or changewithout warning, etc.). In some embodiments, the vehicle event recordercomprises a vehicle event recorder selected by a server system toreceive the request for dynamic event data. In some embodiments, therequest for dynamic event data is received at the vehicle event recorderwhile the vehicle is in service (e.g., while the vehicle is traveling onits route, via a wireless connection, while not at a home station,etc.). In some embodiments, the request for dynamic event data comprisesa time window (e.g., a time window indicating a time range during whichthe request for dynamic event data is in effect). For example, the timewindow typically begins soon after receiving the request for dynamicevent data (e.g., immediately, less than a second, less than a minute,less than an hour, or less than a day). In 1202, a location and aconfiguration setting are extracted from the request. For example, thelocation and the configuration are received as part of the request or inseparate (e.g., one or more than one) communications to the vehicleevent recorder. In 1204, a setting associated with collection of thedynamic event data is modified according to the configuration setting,wherein the dynamic event data is collected using one or more sensors.For example, the configuration setting comprises a video sample rate, avideo resolution, a sensor sample rate, a sensor resolution, or a set ofsensors for data collection, or any other appropriate configurationsetting. In some embodiments, the setting is modified only while thevehicle is determined to be within a geofence region (e.g., a geofenceregion associated with the request for dynamic event data). For example,the setting is modified when the vehicle event recorder is close to thelocation where the desired dynamic event data is located and/or orientedtoward the location of or able to take the dynamic event data location.In 1206, it is determined whether the vehicle event recorder is locatedappropriately to record the dynamic event data using the one or moresensors. In the event it is determined that the vehicle event recorderis not located appropriately to record the dynamic event data using theone or more sensors, control passes to 1212. In the event it isdetermined that the vehicle event recorder is located appropriately torecord the dynamic event data using the one or more sensors, controlpasses to 1208. In 1208, the dynamic event data is recorded from the oneor more sensors. In 1210, the dynamic event data is provided (e.g., tothe server system). In 1212, it is determined whether the dynamic eventhas moved. For example, it is determined whether the dynamic event hasmoved based at least in part on observing the dynamic event in motion,on observing the dynamic event not present in the location indicated, onreceiving an indication that the dynamic event has moved, etc. Forexample, a deer or road sweeping crew is moving close to on the road. Inthe event it is determined that the dynamic event has not moved, controlpasses to 1216. In the event it is determined that the dynamic event hasmoved, control passes to 1214. In 1214, an indication is provided thatthe dynamic event has moved (e.g., to the server system). In 1216, it isdetermined whether to continue checking (e.g., checking whether thevehicle event recorder is located appropriate to record the dynamicevent data using the one or more sensors). In some embodiments, adetermination whether or not to continue checking is based at least inpart on a time window (e.g., a time window associated with the requestfor dynamic event data). In the event it is determined to continuechecking, control passes to 1206. In the event it is determined not tocontinue checking, the process ends.

FIG. 13 is a flow diagram illustrating an embodiment of a process fordetermining whether a vehicle event recorder is located appropriately torecord the dynamic event data using one or more sensors. In someembodiments, the process of FIG. 13 implements 1206 of FIG. 12 . In theexample shown, in 1300, it is determined whether the vehicle eventrecorder is within a threshold distance of the location. For example, itis determined whether the vehicle event recorder is within a thresholddistance of the location associated with the request based at least inpart on a GPS measurement. In the event it is determined that thevehicle event recorder is not within a threshold distance of thelocation, the process ends. In the event it is determined that thevehicle event recorder is within a threshold distance of the location,control passes to 1302. In 1302, it is determined whether the vehicleevent recorder is receiving data from a sensor oriented toward thelocation. For example, it is determined whether the vehicle eventrecorder is receiving data from a sensor oriented toward the location ofthe request based at least in part on sensor orientation information(e.g., a relative orientation associated with a set of sensors mountedon the vehicle) and a set of GPS measurements or a GPS measurement and acompass measurement. In the event it is determined that the vehicleevent recorder is not receiving data from a sensor oriented toward thelocation, the process ends. In the event it is determined that thevehicle event recorder is receiving data from a sensor oriented towardthe location, control passes to 1304. In 1304, additional locationconstraints and/or direction constraints are determined. For example,additional location constraints and/or direction constraints comprise atighter distance threshold, a constraint depending on both distance andorientation, a constraint dependent on number of other vehicles present,a constraint dependent on time of day, a constraint dependent on vehicletravel speed, a constraint based on buildings or other obstructions thatrestrict sensor abilities to detect an event, etc. In some embodiments,additional location constraints comprise model-based constraints (e.g.,does a model-based processing of a sensor input indicate that thevehicle event recorder is able to acquire sensor data related to thelocation of a location-based data identification job). In someembodiments, no additional location and/or direction constraints aredetermined. In 1306, it is determined whether the additional locationconstraints and/or direction constraints are satisfied. For example, thevehicle event recorder is within a tighter distance threshold, within adistance and oriented appropriately (e.g., facing the location of theevent), is in the presence of a threshold number of vehicles, is attime, after a time, before a time, or within a threshold time window, iswithin a vehicle speed range, above a speed threshold, below a speedthreshold, located oriented to avoid local obstructions, etc. In theevent it is determined that the additional location constraints and/ordirection constraints are not satisfied, the process ends. In the eventit is determined that the additional location constraints and/ordirection constraints are satisfied, control passes to 1308. In 1308,the process indicates that the vehicle is able to acquire sensor datarelated to the location of the location-based data identification job.

FIG. 14 is a flow diagram illustrating an embodiment of a process for ainitiating a dynamic request to capture dynamic event data. In someembodiments, the process of FIG. 14 is executed by vehicle data center108 of FIG. 1 . In the example shown, in 1400, an indication of adynamic event is received. In some embodiments, the indication of thedynamic event is received from a vehicle event recorder. In 1402, arequest for dynamic event data is determined, wherein the requestcomprises a location and a configuration setting. For example, thelocation comprises the location of the dynamic event and theconfiguration setting comprises a configuration setting enabling bettercapture of dynamic event data (e.g., a high video resolutionconfiguration setting, a high video frame rate configuration setting, ahigh audio sample rate, a high accelerometer power level, etc.). In1404, a plurality of vehicle event recorders to receive the request fordynamic event data is determined. For example, the plurality of vehicleevent recorders comprises a plurality of vehicle event recorders nearthe dynamic event location or whose planned route takes them near thedynamic event location. In various embodiments, the plurality of vehicleevent recorders comprises a plurality of vehicle event recordersselected based in part on an associated vehicle route, on vehicle eventrecorder processor capabilities, on vehicle event recorder associatedsensors, on a current location, on a known future location, or based onany other appropriate data. In 1406, the request for dynamic event datais provided to the plurality of vehicle event recorders. In 1408,dynamic event data is received from a vehicle event recorder. In 1410,additional requests for dynamic event data are created and provided, ifnecessary.

FIG. 15 is a flow diagram illustrating an embodiment of a process forcreating additional requests for dynamic event data in the event that adynamic event has changed location. In some embodiments, the process ofFIG. 15 implements 1410 of FIG. 14 in the event that the dynamic eventhas changed location. In the example shown, in 1500, it is determinedthat the event associated with the dynamic event data has moved to a newlocation. For example, it is determined that the event associated withthe dynamic event data has moved to a new location based at least inpart on a new indication of a dynamic event or it is determined that theevent associated with the dynamic event data has moved to a new locationbased at least in part on a known rate of movement for the dynamic event(e.g., as received in the request or determined using motiondetermination/analysis performed on received video data) or a newdetected location (e.g., using GPS location of the vehicle and sensordetermination). In 1502, a new request for dynamic event data comprisingthe location is determined. In 1504, a new plurality of vehicle eventrecorders to receive the new request for dynamic event data isdetermined. In 1506, the new request for dynamic event data is providedto the new plurality of vehicle event recorders to receive the newrequest for dynamic event data.

FIG. 16 is a flow diagram illustrating an embodiment of a process forcreating additional requests for dynamic event data in the event that aconfiguration setting requires modification. In some embodiments, theprocess of FIG. 16 implements 1410 of FIG. 14 in the event that theconfiguration setting requires modification. In the example shown, in1600, it is determined that a configuration setting requiresmodification. For example, it is determined that a configuration settingrequires modification based at least in part on a received dynamic eventdata not being of high enough quality. In 1602, a new configurationsetting is determined. For example, the new configuration setting isdetermined based at least in part on the received dynamic event data. In1604, a new request for dynamic event data comprising the newconfiguration setting is determined. For example, the new request fordynamic event data is based at least in part on the dynamic event data.In various embodiments, the new configuration setting comprises a highersensor resolution, a higher video frame rate, a higher sensor samplerate, an additional sensor for data capture, or any other appropriateconfiguration setting. In some embodiments, the new request for dynamicevent data comprises an indication to immediately capture data at thenew configuration setting. In 1606, a new plurality of vehicle eventrecorders to receive the new request for dynamic event data isdetermined. For example, a set of vehicle event recorders are determinedto receive the new request for dynamic event data based on location,vehicle route, orientation, etc. In 1608, the new request for dynamicevent data is provided to the new plurality of vehicle event recordersto receive the new request for dynamic event data.

Although the foregoing embodiments have been described in some detailfor purposes of clarity of understanding, the invention is not limitedto the details provided. There are many alternative ways of implementingthe invention. The disclosed embodiments are illustrative and notrestrictive.

What is claimed is:
 1. A system, comprising: an interface configured toreceive a location-based data description for capturing a location-baseddata; and a processor configured to: determine a location based at leastin part on the location-based data description; create a location-baseddata identification job based at least in part on the location; causeexecution of the location-based data identification job to a set ofvehicle event recorder systems, wherein the location-based dataidentification job is executed by a vehicle event recorder system of theset of vehicle event recorder systems to acquire sensor data in responseto a vehicle being able to acquire the sensor data related to thelocation of the location-based data identification job, and wherein thecausing of the execution of the location-based data identification jobto the set of vehicle event recorder systems comprises to: perform oneor more of the following: A) determine that a time bound has not beenreached; and in response to a determination that the time bound has notbeen reached:  determine that the location-based data satisfies afrequency constraint, wherein the frequency constraint relates to atleast a threshold number of times within a predetermined period of time;and  in response to a determination that the location-based datasatisfies the frequency constraint, provide an indication to the vehicleevent recorder system to not execute the location-based dataidentification job for a period of time; or B) determine that a geofenceregion associated with the location-based data has been entered; and inresponse to a determination that the geofence region associated with thelocation-based data has been entered:  determine that the vehicle eventrecorder system is receiving data from a sensor oriented toward thelocation; and  in response to a determination that the vehicle eventrecorder system is receiving data from a sensor oriented toward thelocation, execute the location-based data identification job; receivethe sensor data from the vehicle event recorder system; and determinethe location-based data based at least in part on the sensor data. 2.The system of claim 1, wherein being able to acquire the sensor datarelated to the location of the location-based data identification jobcomprises being within a threshold distance from the location.
 3. Thesystem of claim 1, wherein being able to acquire the sensor data relatedto the location of the location-based data identification job comprisesreceiving data from a sensor oriented toward the location.
 4. The systemof claim 1, wherein the geofence region comprises a geographicalperimeter or a road segment.
 5. The system of claim 1, wherein thevehicle event recorder system is additionally configured to determinewhether the vehicle is able to acquire the sensor data related to thelocation of the location-based data identification job while the vehicleis within the geofence region.
 6. The system of claim 1, wherein theprocessor is additionally configured to determine a target based atleast in part on the location-based data description.
 7. The system ofclaim 6, wherein the location-based data identification job is based atleast in part on the target.
 8. The system of claim 6, wherein thetarget comprises a road sign, a billboard, a building, a road feature,or a construction zone.
 9. The system of claim 1, wherein the processoris additionally configured to determine angle constraints and/ordirection constraints for image capture.
 10. The system of claim 9,wherein the vehicle being able to acquire the sensor data comprisessatisfying the angle constraints and/or the direction constraints. 11.The system of claim 1, wherein the processor is further configured todetermine a model-based system comprising a portion of thelocation-based data identification job.
 12. The system of claim 1,wherein the location-based data identification job additionallycomprises a recognition frequency.
 13. The system of claim 1, whereinthe processor is further configured to: determine that the time boundhas been reached; and provide an indication to cease execution of thelocation-based data identification job.
 14. The system of claim 1,wherein the processor is further configured to determine whetherpreviously captured data satisfies the location-based data description.15. The system of claim 1, wherein the location-based dataidentification job comprises determining whether previously captureddata stored on the vehicle event recorder satisfies the location-baseddata description.
 16. The system of claim 1, wherein the processor isfurther configured to cause sending of the sensor data from the vehicleevent recorder system.
 17. The system of claim 1, wherein the set ofvehicle event recorder systems is determined based on tenant or clientpermissions, location permissions, business rules, legal locationpermissions, federal laws, state laws, or local laws.
 18. The system ofclaim 1, wherein the causing of the execution of the location-based dataidentification job to the set of vehicle event recorder systemscomprises to: determine that a time bound has not been reached; and inresponse to a determination that the time bound has not been reached:determine that the location-based data satisfies a frequency constraint,wherein the frequency constraint relates to at least a threshold numberof times within a predetermined period of time; and in response to adetermination that the location-based data satisfies the frequencyconstraint, provide an indication to the vehicle event recorder systemto not execute the location-based data identification job for a periodof time.
 19. The system of claim 1, wherein the causing of the executionof the location-based data identification job to the set of vehicleevent recorder systems comprises to: determine that a geofence regionassociated with the location-based data has been entered; and inresponse to a determination that the geofence region associated with thelocation-based data has been entered: determine that the vehicle eventrecorder system is receiving data from a sensor oriented toward thelocation; and in response to a determination that the vehicle eventrecorder system is receiving data from a sensor oriented toward thelocation, execute the location-based data identification job.
 20. Amethod, comprising: receiving a location-based data description forcapturing a location-based data; determining a location based at leastin part on the location-based data description; creating alocation-based data identification job based at least in part on thelocation; causing execution of the location-based data identificationjob to a set of vehicle event recorder systems, wherein thelocation-based data identification job is executed by a vehicle eventrecorder system of the set of vehicle event recorder systems to acquiresensor data in response to a vehicle being able to acquire the sensordata related to the location of the location-based data identificationjob, and wherein the causing of the execution of the location-based dataidentification job to the set of vehicle event recorder systemscomprises: performing one or more of the following: A) determining thata time bound has not been reached; and in response to a determinationthat the time bound has not been reached: determining that thelocation-based data satisfies a frequency constraint, wherein thefrequency constraint relates to at least a threshold number of timeswithin a predetermined period of time; and in response to adetermination that the location-based data satisfies the frequencyconstraint, providing an indication to the vehicle event recorder systemto not execute the location-based data identification job for a periodof time; or B) determining that a geofence region associated with thelocation-based data has been entered; and in response to a determinationthat the geofence region associated with the location-based data hasbeen entered: determining that the vehicle event recorder system isreceiving data from a sensor oriented toward the location; and inresponse to a determination that the vehicle event recorder system isreceiving data from a sensor oriented toward the location, executing thelocation-based data identification job; receiving the sensor data fromthe vehicle event recorder system; and determining the location-baseddata based at least in part on the sensor data.
 21. A computer programproduct, the computer program product being embodied in a non-transitorycomputer readable storage medium and comprising computer instructionsfor: receiving a location-based data description for capturing alocation-based data; determining a location based at least in part onthe location-based data description; creating a location-based dataidentification job based at least in part on the location; causingexecution of the location-based data identification job to a set ofvehicle event recorder systems, wherein the location-based dataidentification job is executed by a vehicle event recorder system of theset of vehicle event recorder systems to acquire sensor data in responseto a vehicle being able to acquire the sensor data related to thelocation of the location-based data identification job, and wherein thecausing of the execution of the location-based data identification jobto the set of vehicle event recorder systems comprises: performing oneor more of the following: A) determining that a time bound has not beenreached; and in response to a determination that the time bound has notbeen reached: determining that the location-based data satisfies afrequency constraint, wherein the frequency constraint relates to atleast a threshold number of times within a predetermined period of time;and in response to a determination that the location-based datasatisfies the frequency constraint, providing an indication to thevehicle event recorder system to not execute the location-based dataidentification job for a period of time; or B) determining that ageofence region associated with the location-based data has beenentered; and in response to a determination that the geofence regionassociated with the location-based data has been entered: determiningthat the vehicle event recorder system is receiving data from a sensororiented toward the location; and in response to a determination thatthe vehicle event recorder system is receiving data from a sensororiented toward the location, executing the location-based dataidentification job; receiving the sensor data from the vehicle eventrecorder system; and determining the location-based data based at leastin part on the sensor data.